Autonomous Error Correction in a Multi-Application Platform

ABSTRACT

An embodiment may involve, based on a pre-defined trigger associated with a particular application, reading error data from a resource that is used by the particular application, wherein persistent storage contains definitions of a plurality of error scenarios, a plurality of fix scripts, and associations between each of the plurality of error scenarios and one or more of the plurality of fix scripts; applying one or more rules to the error data, wherein the rules involve pattern matching or parsing; based on applying the one or more rules, determining a particular error scenario represented in the error data, wherein the particular error scenario is one of the plurality of error scenarios; determining, based on the associations, a particular fix script associated with the particular error scenario, wherein the particular fix script is one of the plurality of fix scripts; and causing execution of the particular fix script.

BACKGROUND

Multi-application platforms, such as remote network managementplatforms, consist of numerous software applications, programs, modules,and scripts. It is inevitable that at least some of these willexperience errors (e.g., instability, incorrect operation, and/orundesirable behavior) from time to time. It can be challenging toidentify when such behavior occurs, much less determine how to rectifythe situation. This leads to long detection and resolution cycles,perhaps stretching out over hours or days, thus having a deleteriousimpact on user experience.

SUMMARY

The embodiments herein address these and potentially other problems byproviding techniques for automated error detection and correction inmulti-application platforms. In particular, an error scenario mapper isconfigured to receive and/or read input information that was produced byor related to the execution of various applications. Error scenarios aredefined as sets of one or more events, patterns, output values,behaviors, and so on relating to one or more of these applications. Eacherror scenario is associated with one or more “fix scripts”, which areprograms that attempt to rectify the associated error. When the errorscenario mapper matches the input information to a predefined errorscenario, it triggers execution of the associated fix scripts. As aresult, errors can be addressed and possibly resolved in a matter ofseconds or minutes without human intervention. In many cases, errors canbe resolved so quickly that users are not even aware of theiroccurrence.

Accordingly, a first example embodiment may involve persistent storagecontaining an error identifier application, an error scenario mappingapplication, definitions of a plurality of error scenarios, a pluralityof fix scripts, and associations between each of the plurality of errorscenarios and one or more of the plurality of fix scripts. One or moreprocessors may be configured to: (i) possibly based on a pre-definedtrigger associated with a particular application configured to executeon the system, read, by the error identifier application, error datafrom a resource that is stored on the system that is used by theparticular application; (ii) apply, by the error scenario mappingapplication, one or more rules to the error data, wherein the rulesinvolve pattern matching or parsing; (iii) possibly based on applyingthe one or more rules, determine, by the error scenario mappingapplication, a particular error scenario represented in the error data,wherein the particular error scenario is one of the plurality of errorscenarios; (iv) determine, by the error scenario mapping application andbased on the associations, a particular fix script associated with theparticular error scenario, wherein the particular fix script is one ofthe plurality of fix scripts; and (v) cause execution of the particularfix script.

A second example embodiment may involve, possibly based on a pre-definedtrigger associated with a particular application, reading, by an erroridentifier application, error data from a resource that is used by theparticular application, wherein persistent storage contains definitionsof a plurality of error scenarios, a plurality of fix scripts, andassociations between each of the plurality of error scenarios and one ormore of the plurality of fix scripts. The second example embodiment mayalso involve applying, by an error scenario mapping application, one ormore rules to the error data, wherein the rules involve pattern matchingor parsing. The second example embodiment may also involve, possiblybased on applying the one or more rules, determining, by the errorscenario mapping application, a particular error scenario represented inthe error data, wherein the particular error scenario is one of theplurality of error scenarios. The second example embodiment may alsoinvolve determining, by the error scenario mapping application and basedon the associations, a particular fix script associated with theparticular error scenario, wherein the particular fix script is one ofthe plurality of fix scripts. The second example embodiment may alsoinvolve causing execution of the particular fix script.

In a third example embodiment, an article of manufacture may include anon-transitory computer-readable medium, having stored thereon programinstructions that, upon execution by a computing system, cause thecomputing system to perform operations in accordance with the firstand/or second example embodiment.

In a fourth example embodiment, a computing system may include at leastone processor, as well as memory and program instructions. The programinstructions may be stored in the memory, and upon execution by the atleast one processor, cause the computing system to perform operations inaccordance with the first and/or second example embodiment.

In a fifth example embodiment, a system may include various means forcarrying out each of the operations of the first and/or second exampleembodiment.

These, as well as other embodiments, aspects, advantages, andalternatives, will become apparent to those of ordinary skill in the artby reading the following detailed description, with reference whereappropriate to the accompanying drawings. Further, this summary andother descriptions and figures provided herein are intended toillustrate embodiments by way of example only and, as such, thatnumerous variations are possible. For instance, structural elements andprocess steps can be rearranged, combined, distributed, eliminated, orotherwise changed, while remaining within the scope of the embodimentsas claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a schematic drawing of a computing device, inaccordance with example embodiments.

FIG. 2 illustrates a schematic drawing of a server device cluster, inaccordance with example embodiments.

FIG. 3 depicts a remote network management architecture, in accordancewith example embodiments.

FIG. 4 depicts a communication environment involving a remote networkmanagement architecture, in accordance with example embodiments.

FIG. 5A depicts another communication environment involving a remotenetwork management architecture, in accordance with example embodiments.

FIG. 5B is a flow chart, in accordance with example embodiments.

FIG. 6 depicts an architecture for autonomous error correction, inaccordance with example embodiments.

FIG. 7 depicts sources of error indications within a multi-applicationplatform, in accordance with example embodiments.

FIG. 8 is a flow chart, in accordance with example embodiments.

DETAILED DESCRIPTION

Example methods, devices, and systems are described herein. It should beunderstood that the words “example” and “exemplary” are used herein tomean “serving as an example, instance, or illustration.” Any embodimentor feature described herein as being an “example” or “exemplary” is notnecessarily to be construed as preferred or advantageous over otherembodiments or features unless stated as such. Thus, other embodimentscan be utilized and other changes can be made without departing from thescope of the subject matter presented herein.

Accordingly, the example embodiments described herein are not meant tobe limiting. It will be readily understood that the aspects of thepresent disclosure, as generally described herein, and illustrated inthe figures, can be arranged, substituted, combined, separated, anddesigned in a wide variety of different configurations. For example, theseparation of features into “client” and “server” components may occurin a number of ways.

Further, unless context suggests otherwise, the features illustrated ineach of the figures may be used in combination with one another. Thus,the figures should be generally viewed as component aspects of one ormore overall embodiments, with the understanding that not allillustrated features are necessary for each embodiment.

Additionally, any enumeration of elements, blocks, or steps in thisspecification or the claims is for purposes of clarity. Thus, suchenumeration should not be interpreted to require or imply that theseelements, blocks, or steps adhere to a particular arrangement or arecarried out in a particular order.

Introduction

A large enterprise is a complex entity with many interrelatedoperations. Some of these are found across the enterprise, such as humanresources (HR), supply chain, information technology (IT), and finance.However, each enterprise also has its own unique operations that provideessential capabilities and/or create competitive advantages.

To support widely-implemented operations, enterprises typically useoff-the-shelf software applications, such as customer relationshipmanagement (CRM) and human capital management (HCM) packages. However,they may also need custom software applications to meet their own uniquerequirements. A large enterprise often has dozens or hundreds of thesecustom software applications. Nonetheless, the advantages provided bythe embodiments herein are not limited to large enterprises and may beapplicable to an enterprise, or any other type of organization, of anysize.

Many such software applications are developed by individual departmentswithin the enterprise. These range from simple spreadsheets tocustom-built software tools and databases. But the proliferation ofsiloed custom software applications has numerous disadvantages. Itnegatively impacts an enterprise's ability to run and grow itsoperations, innovate, and meet regulatory requirements. The enterprisemay find it difficult to integrate, streamline, and enhance itsoperations due to lack of a single system that unifies its subsystemsand data.

To efficiently create custom applications, enterprises would benefitfrom a remotely-hosted application platform that eliminates unnecessarydevelopment complexity. The goal of such a platform would be to reducetime-consuming, repetitive application development tasks so thatsoftware engineers and individuals in other roles can focus ondeveloping unique, high-value features.

In order to achieve this goal, the concept of Application Platform as aService (aPaaS) is introduced, to intelligently automate workflowsthroughout the enterprise. An aPaaS system is hosted remotely from theenterprise, but may access data, applications, and services within theenterprise by way of secure connections. Such an aPaaS system may have anumber of advantageous capabilities and characteristics. Theseadvantages and characteristics may be able to improve the enterprise'soperations and workflows for IT, HR, CRM, customer service, applicationdevelopment, and security.

The aPaaS system may support development and execution ofmodel-view-controller (MVC) applications. MVC applications divide theirfunctionality into three interconnected parts (model, view, andcontroller) in order to isolate representations of information from themanner in which the information is presented to the user, therebyallowing for efficient code reuse and parallel development. Theseapplications may be web-based, and offer create, read, update, anddelete (CRUD) capabilities. This allows new applications to be built ona common application infrastructure.

The aPaaS system may support standardized application components, suchas a standardized set of widgets for graphical user interface (GUI)development. In this way, applications built using the aPaaS system havea common look and feel. Other software components and modules may bestandardized as well. In some cases, this look and feel can be brandedor skinned with an enterprise's custom logos and/or color schemes.

The aPaaS system may support the ability to configure the behavior ofapplications using metadata. This allows application behaviors to berapidly adapted to meet specific needs. Such an approach reducesdevelopment time and increases flexibility. Further, the aPaaS systemmay support GUI tools that facilitate metadata creation and management,thus reducing errors in the metadata.

The aPaaS system may support clearly-defined interfaces betweenapplications, so that software developers can avoid unwantedinter-application dependencies. Thus, the aPaaS system may implement aservice layer in which persistent state information and other data arestored.

The aPaaS system may support a rich set of integration features so thatthe applications thereon can interact with legacy applications andthird-party applications. For instance, the aPaaS system may support acustom employee-onboarding system that integrates with legacy HR, IT,and accounting systems.

The aPaaS system may support enterprise-grade security. Furthermore,since the aPaaS system may be remotely hosted, it should also utilizesecurity procedures when it interacts with systems in the enterprise orthird-party networks and services hosted outside of the enterprise. Forexample, the aPaaS system may be configured to share data amongst theenterprise and other parties to detect and identify common securitythreats.

Other features, functionality, and advantages of an aPaaS system mayexist. This description is for purpose of example and is not intended tobe limiting.

As an example of the aPaaS development process, a software developer maybe tasked to create a new application using the aPaaS system. First, thedeveloper may define the data model, which specifies the types of datathat the application uses and the relationships therebetween. Then, viaa GUI of the aPaaS system, the developer enters (e.g., uploads) the datamodel. The aPaaS system automatically creates all of the correspondingdatabase tables, fields, and relationships, which can then be accessedvia an object-oriented services layer.

In addition, the aPaaS system can also build a fully-functional MVCapplication with client-side interfaces and server-side CRUD logic. Thisgenerated application may serve as the basis of further development forthe user. Advantageously, the developer does not have to spend a largeamount of time on basic application functionality. Further, since theapplication may be web-based, it can be accessed from anyInternet-enabled client device. Alternatively or additionally, a localcopy of the application may be able to be accessed, for instance, whenInternet service is not available.

The aPaaS system may also support a rich set of pre-definedfunctionality that can be added to applications. These features includesupport for searching, email, templating, workflow design, reporting,analytics, social media, scripting, mobile-friendly output, andcustomized GUIs.

Such an aPaaS system may represent a GUI in various ways. For example, aserver device of the aPaaS system may generate a representation of a GUIusing a combination of HTML and JAVASCRIPT®. The JAVASCRIPT® may includeclient-side executable code, server-side executable code, or both. Theserver device may transmit or otherwise provide this representation to aclient device for the client device to display on a screen according toits locally-defined look and feel. Alternatively, a representation of aGUI may take other forms, such as an intermediate form (e.g., JAVA®byte-code) that a client device can use to directly generate graphicaloutput therefrom. Other possibilities exist.

Further, user interaction with GUI elements, such as buttons, menus,tabs, sliders, checkboxes, toggles, etc. may be referred to as“selection”, “activation”, or “actuation” thereof. These terms may beused regardless of whether the GUI elements are interacted with by wayof keyboard, pointing device, touchscreen, or another mechanism.

An aPaaS architecture is particularly powerful when integrated with anenterprise's network and used to manage such a network. The followingembodiments describe architectural and functional aspects of exampleaPaaS systems, as well as the features and advantages thereof.

II. Example Computing Devices and Cloud-Based Computing Environments

FIG. 1 is a simplified block diagram exemplifying a computing device100, illustrating some of the components that could be included in acomputing device arranged to operate in accordance with the embodimentsherein. Computing device 100 could be a client device (e.g., a deviceactively operated by a user), a server device (e.g., a device thatprovides computational services to client devices), or some other typeof computational platform. Some server devices may operate as clientdevices from time to time in order to perform particular operations, andsome client devices may incorporate server features.

In this example, computing device 100 includes processor 102, memory104, network interface 106, and input/output unit 108, all of which maybe coupled by system bus 110 or a similar mechanism. In someembodiments, computing device 100 may include other components and/orperipheral devices (e.g., detachable storage, printers, and so on).

Processor 102 may be one or more of any type of computer processingelement, such as a central processing unit (CPU), a co-processor (e.g.,a mathematics, graphics, or encryption co-processor), a digital signalprocessor (DSP), a network processor, and/or a form of integratedcircuit or controller that performs processor operations. In some cases,processor 102 may be one or more single-core processors. In other cases,processor 102 may be one or more multi-core processors with multipleindependent processing units. Processor 102 may also include registermemory for temporarily storing instructions being executed and relateddata, as well as cache memory for temporarily storing recently-usedinstructions and data.

Memory 104 may be any form of computer-usable memory, including but notlimited to random access memory (RAM), read-only memory (ROM), andnon-volatile memory (e.g., flash memory, hard disk drives, solid statedrives, compact discs (CDs), digital video discs (DVDs), and/or tapestorage). Thus, memory 104 represents both main memory units, as well aslong-term storage. Other types of memory may include biological memory.

Memory 104 may store program instructions and/or data on which programinstructions may operate. By way of example, memory 104 may store theseprogram instructions on a non-transitory, computer-readable medium, suchthat the instructions are executable by processor 102 to carry out anyof the methods, processes, or operations disclosed in this specificationor the accompanying drawings.

As shown in FIG. 1, memory 104 may include firmware 104A, kernel 104B,and/or applications 104C. Firmware 104A may be program code used to bootor otherwise initiate some or all of computing device 100. Kernel 104Bmay be an operating system, including modules for memory management,scheduling and management of processes, input/output, and communication.Kernel 104B may also include device drivers that allow the operatingsystem to communicate with the hardware modules (e.g., memory units,networking interfaces, ports, and buses) of computing device 100.Applications 104C may be one or more user-space software programs, suchas web browsers or email clients, as well as any software libraries usedby these programs. Memory 104 may also store data used by these andother programs and applications.

Network interface 106 may take the form of one or more wirelineinterfaces, such as Ethernet (e.g., Fast Ethernet, Gigabit Ethernet, andso on). Network interface 106 may also support communication over one ormore non-Ethernet media, such as coaxial cables or power lines, or overwide-area media, such as Synchronous Optical Networking (SONET) ordigital subscriber line (DSL) technologies. Network interface 106 mayadditionally take the form of one or more wireless interfaces, such asIEEE 802.11 (Wifi), BLUETOOTH®, global positioning system (GPS), or awide-area wireless interface. However, other forms of physical layerinterfaces and other types of standard or proprietary communicationprotocols may be used over network interface 106. Furthermore, networkinterface 106 may comprise multiple physical interfaces. For instance,some embodiments of computing device 100 may include Ethernet,BLUETOOTH®, and Wifi interfaces.

Input/output unit 108 may facilitate user and peripheral deviceinteraction with computing device 100. Input/output unit 108 may includeone or more types of input devices, such as a keyboard, a mouse, a touchscreen, and so on. Similarly, input/output unit 108 may include one ormore types of output devices, such as a screen, monitor, printer, and/orone or more light emitting diodes (LEDs). Additionally or alternatively,computing device 100 may communicate with other devices using auniversal serial bus (USB) or high-definition multimedia interface(HDMI) port interface, for example.

In some embodiments, one or more computing devices like computing device100 may be deployed to support an aPaaS architecture. The exact physicallocation, connectivity, and configuration of these computing devices maybe unknown and/or unimportant to client devices. Accordingly, thecomputing devices may be referred to as “cloud-based” devices that maybe housed at various remote data center locations.

FIG. 2 depicts a cloud-based server cluster 200 in accordance withexample embodiments. In FIG. 2, operations of a computing device (e.g.,computing device 100) may be distributed between server devices 202,data storage 204, and routers 206, all of which may be connected bylocal cluster network 208. The number of server devices 202, datastorages 204, and routers 206 in server cluster 200 may depend on thecomputing task(s) and/or applications assigned to server cluster 200.

For example, server devices 202 can be configured to perform variouscomputing tasks of computing device 100. Thus, computing tasks can bedistributed among one or more of server devices 202. To the extent thatthese computing tasks can be performed in parallel, such a distributionof tasks may reduce the total time to complete these tasks and return aresult. For purposes of simplicity, both server cluster 200 andindividual server devices 202 may be referred to as a “server device.”This nomenclature should be understood to imply that one or moredistinct server devices, data storage devices, and cluster routers maybe involved in server device operations.

Data storage 204 may be data storage arrays that include drive arraycontrollers configured to manage read and write access to groups of harddisk drives and/or solid state drives. The drive array controllers,alone or in conjunction with server devices 202, may also be configuredto manage backup or redundant copies of the data stored in data storage204 to protect against drive failures or other types of failures thatprevent one or more of server devices 202 from accessing units of datastorage 204. Other types of memory aside from drives may be used.

Routers 206 may include networking equipment configured to provideinternal and external communications for server cluster 200. Forexample, routers 206 may include one or more packet-switching and/orrouting devices (including switches and/or gateways) configured toprovide (i) network communications between server devices 202 and datastorage 204 via local cluster network 208, and/or (ii) networkcommunications between server cluster 200 and other devices viacommunication link 210 to network 212.

Additionally, the configuration of routers 206 can be based at least inpart on the data communication requirements of server devices 202 anddata storage 204, the latency and throughput of the local clusternetwork 208, the latency, throughput, and cost of communication link210, and/or other factors that may contribute to the cost, speed,fault-tolerance, resiliency, efficiency, and/or other design goals ofthe system architecture.

As a possible example, data storage 204 may include any form ofdatabase, such as a structured query language (SQL) database. Varioustypes of data structures may store the information in such a database,including but not limited to tables, arrays, lists, trees, and tuples.Furthermore, any databases in data storage 204 may be monolithic ordistributed across multiple physical devices.

Server devices 202 may be configured to transmit data to and receivedata from data storage 204. This transmission and retrieval may take theform of SQL queries or other types of database queries, and the outputof such queries, respectively. Additional text, images, video, and/oraudio may be included as well. Furthermore, server devices 202 mayorganize the received data into web page or web applicationrepresentations. Such a representation may take the form of a markuplanguage, such as the hypertext markup language (HTML), the extensiblemarkup language (XML), or some other standardized or proprietary format.Moreover, server devices 202 may have the capability of executingvarious types of computerized scripting languages, such as but notlimited to Perl, Python, PHP Hypertext Preprocessor (PHP), Active ServerPages (ASP), JAVASCRIPT®, and so on. Computer program code written inthese languages may facilitate the providing of web pages to clientdevices, as well as client device interaction with the web pages.Alternatively or additionally, JAVA® may be used to facilitategeneration of web pages and/or to provide web application functionality.

III. Example Remote Network Management Architecture

FIG. 3 depicts a remote network management architecture, in accordancewith example embodiments. This architecture includes three maincomponents—managed network 300, remote network management platform 320,and public cloud networks 340—all connected by way of Internet 350.

A. Managed Networks

Managed network 300 may be, for example, an enterprise network used byan entity for computing and communications tasks, as well as storage ofdata. Thus, managed network 300 may include client devices 302, serverdevices 304, routers 306, virtual machines 308, firewall 310, and/orproxy servers 312. Client devices 302 may be embodied by computingdevice 100, server devices 304 may be embodied by computing device 100or server cluster 200, and routers 306 may be any type of router,switch, or gateway.

Virtual machines 308 may be embodied by one or more of computing device100 or server cluster 200. In general, a virtual machine is an emulationof a computing system, and mimics the functionality (e.g., processor,memory, and communication resources) of a physical computer. Onephysical computing system, such as server cluster 200, may support up tothousands of individual virtual machines. In some embodiments, virtualmachines 308 may be managed by a centralized server device orapplication that facilitates allocation of physical computing resourcesto individual virtual machines, as well as performance and errorreporting.

Enterprises often employ virtual machines in order to allocate computingresources in an efficient, as needed fashion. Providers of virtualizedcomputing systems include VMWARE® and MICROSOFT®.

Firewall 310 may be one or more specialized routers or server devicesthat protect managed network 300 from unauthorized attempts to accessthe devices, applications, and services therein, while allowingauthorized communication that is initiated from managed network 300.Firewall 310 may also provide intrusion detection, web filtering, virusscanning, application-layer gateways, and other applications orservices. In some embodiments not shown in FIG. 3, managed network 300may include one or more virtual private network (VPN) gateways withwhich it communicates with remote network management platform 320 (seebelow).

Managed network 300 may also include one or more proxy servers 312. Anembodiment of proxy servers 312 may be a server application thatfacilitates communication and movement of data between managed network300, remote network management platform 320, and public cloud networks340. In particular, proxy servers 312 may be able to establish andmaintain secure communication sessions with one or more computationalinstances of remote network management platform 320. By way of such asession, remote network management platform 320 may be able to discoverand manage aspects of the architecture and configuration of managednetwork 300 and its components. Possibly with the assistance of proxyservers 312, remote network management platform 320 may also be able todiscover and manage aspects of public cloud networks 340 that are usedby managed network 300.

Firewalls, such as firewall 310, typically deny all communicationsessions that are incoming by way of Internet 350, unless such a sessionwas ultimately initiated from behind the firewall (i.e., from a deviceon managed network 300) or the firewall has been explicitly configuredto support the session. By placing proxy servers 312 behind firewall 310(e.g., within managed network 300 and protected by firewall 310), proxyservers 312 may be able to initiate these communication sessions throughfirewall 310. Thus, firewall 310 might not have to be specificallyconfigured to support incoming sessions from remote network managementplatform 320, thereby avoiding potential security risks to managednetwork 300.

In some cases, managed network 300 may consist of a few devices and asmall number of networks. In other deployments, managed network 300 mayspan multiple physical locations and include hundreds of networks andhundreds of thousands of devices. Thus, the architecture depicted inFIG. 3 is capable of scaling up or down by orders of magnitude.

Furthermore, depending on the size, architecture, and connectivity ofmanaged network 300, a varying number of proxy servers 312 may bedeployed therein. For example, each one of proxy servers 312 may beresponsible for communicating with remote network management platform320 regarding a portion of managed network 300. Alternatively oradditionally, sets of two or more proxy servers may be assigned to sucha portion of managed network 300 for purposes of load balancing,redundancy, and/or high availability.

B. Remote Network Management Platforms

Remote network management platform 320 is a hosted environment thatprovides aPaaS services to users, particularly to the operator ofmanaged network 300. These services may take the form of web-basedportals, for example, using the aforementioned web-based technologies.Thus, a user can securely access remote network management platform 320from, for example, client devices 302, or potentially from a clientdevice outside of managed network 300. By way of the web-based portals,users may design, test, and deploy applications, generate reports, viewanalytics, and perform other tasks.

As shown in FIG. 3, remote network management platform 320 includes fourcomputational instances 322, 324, 326, and 328. Each of thesecomputational instances may represent one or more server nodes operatingdedicated copies of the aPaaS software and/or one or more databasenodes. The arrangement of server and database nodes on physical serverdevices and/or virtual machines can be flexible and may vary based onenterprise needs. In combination, these nodes may provide a set of webportals, services, and applications (e.g., a wholly-functioning aPaaSsystem) available to a particular enterprise. In some cases, a singleenterprise may use multiple computational instances.

For example, managed network 300 may be an enterprise customer of remotenetwork management platform 320, and may use computational instances322, 324, and 326. The reason for providing multiple computationalinstances to one customer is that the customer may wish to independentlydevelop, test, and deploy its applications and services. Thus,computational instance 322 may be dedicated to application developmentrelated to managed network 300, computational instance 324 may bededicated to testing these applications, and computational instance 326may be dedicated to the live operation of tested applications andservices. A computational instance may also be referred to as a hostedinstance, a remote instance, a customer instance, or by some otherdesignation. Any application deployed onto a computational instance maybe a scoped application, in that its access to databases within thecomputational instance can be restricted to certain elements therein(e.g., one or more particular database tables or particular rows withinone or more database tables).

For purposes of clarity, the disclosure herein refers to the arrangementof application nodes, database nodes, aPaaS software executing thereon,and underlying hardware as a “computational instance.” Note that usersmay colloquially refer to the graphical user interfaces provided therebyas “instances.” But unless it is defined otherwise herein, a“computational instance” is a computing system disposed within remotenetwork management platform 320.

The multi-instance architecture of remote network management platform320 is in contrast to conventional multi-tenant architectures, overwhich multi-instance architectures exhibit several advantages. Inmulti-tenant architectures, data from different customers (e.g.,enterprises) are comingled in a single database. While these customers'data are separate from one another, the separation is enforced by thesoftware that operates the single database. As a consequence, a securitybreach in this system may impact all customers' data, creatingadditional risk, especially for entities subject to governmental,healthcare, and/or financial regulation. Furthermore, any databaseoperations that impact one customer will likely impact all customerssharing that database. Thus, if there is an outage due to hardware orsoftware errors, this outage affects all such customers. Likewise, ifthe database is to be upgraded to meet the needs of one customer, itwill be unavailable to all customers during the upgrade process. Often,such maintenance windows will be long, due to the size of the shareddatabase.

In contrast, the multi-instance architecture provides each customer withits own database in a dedicated computing instance. This preventscomingling of customer data, and allows each instance to beindependently managed. For example, when one customer's instanceexperiences an outage due to errors or an upgrade, other computationalinstances are not impacted. Maintenance down time is limited because thedatabase only contains one customer's data. Further, the simpler designof the multi-instance architecture allows redundant copies of eachcustomer database and instance to be deployed in a geographicallydiverse fashion. This facilitates high availability, where the liveversion of the customer's instance can be moved when faults are detectedor maintenance is being performed.

In some embodiments, remote network management platform 320 may includeone or more central instances, controlled by the entity that operatesthis platform. Like a computational instance, a central instance mayinclude some number of application and database nodes disposed upon somenumber of physical server devices or virtual machines. Such a centralinstance may serve as a repository for specific configurations ofcomputational instances as well as data that can be shared amongst atleast some of the computational instances. For instance, definitions ofcommon security threats that could occur on the computational instances,software packages that are commonly discovered on the computationalinstances, and/or an application store for applications that can bedeployed to the computational instances may reside in a centralinstance. Computational instances may communicate with central instancesby way of well-defined interfaces in order to obtain this data.

In order to support multiple computational instances in an efficientfashion, remote network management platform 320 may implement aplurality of these instances on a single hardware platform. For example,when the aPaaS system is implemented on a server cluster such as servercluster 200, it may operate virtual machines that dedicate varyingamounts of computational, storage, and communication resources toinstances. But full virtualization of server cluster 200 might not benecessary, and other mechanisms may be used to separate instances. Insome examples, each instance may have a dedicated account and one ormore dedicated databases on server cluster 200. Alternatively, acomputational instance such as computational instance 322 may spanmultiple physical devices.

In some cases, a single server cluster of remote network managementplatform 320 may support multiple independent enterprises. Furthermore,as described below, remote network management platform 320 may includemultiple server clusters deployed in geographically diverse data centersin order to facilitate load balancing, redundancy, and/or highavailability.

C. Public Cloud Networks

Public cloud networks 340 may be remote server devices (e.g., aplurality of server clusters such as server cluster 200) that can beused for outsourced computation, data storage, communication, andservice hosting operations. These servers may be virtualized (i.e., theservers may be virtual machines). Examples of public cloud networks 340may include AMAZON WEB SERVICES® and MICROSOFT® AZURE®. Like remotenetwork management platform 320, multiple server clusters supportingpublic cloud networks 340 may be deployed at geographically diverselocations for purposes of load balancing, redundancy, and/or highavailability.

Managed network 300 may use one or more of public cloud networks 340 todeploy applications and services to its clients and customers. Forinstance, if managed network 300 provides online music streamingservices, public cloud networks 340 may store the music files andprovide web interface and streaming capabilities. In this way, theenterprise of managed network 300 does not have to build and maintainits own servers for these operations.

Remote network management platform 320 may include modules thatintegrate with public cloud networks 340 to expose virtual machines andmanaged services therein to managed network 300. The modules may allowusers to request virtual resources, discover allocated resources, andprovide flexible reporting for public cloud networks 340. In order toestablish this functionality, a user from managed network 300 mightfirst establish an account with public cloud networks 340, and request aset of associated resources. Then, the user may enter the accountinformation into the appropriate modules of remote network managementplatform 320. These modules may then automatically discover themanageable resources in the account, and also provide reports related tousage, performance, and billing.

D. Communication Support and Other Operations

Internet 350 may represent a portion of the global Internet. However,Internet 350 may alternatively represent a different type of network,such as a private wide-area or local-area packet-switched network.

FIG. 4 further illustrates the communication environment between managednetwork 300 and computational instance 322, and introduces additionalfeatures and alternative embodiments. In FIG. 4, computational instance322 is replicated, in whole or in part, across data centers 400A and400B. These data centers may be geographically distant from one another,perhaps in different cities or different countries. Each data centerincludes support equipment that facilitates communication with managednetwork 300, as well as remote users.

In data center 400A, network traffic to and from external devices flowseither through VPN gateway 402A or firewall 404A. VPN gateway 402A maybe peered with VPN gateway 412 of managed network 300 by way of asecurity protocol such as Internet Protocol Security (IPSEC) orTransport Layer Security (TLS). Firewall 404A may be configured to allowaccess from authorized users, such as user 414 and remote user 416, andto deny access to unauthorized users. By way of firewall 404A, theseusers may access computational instance 322, and possibly othercomputational instances. Load balancer 406A may be used to distributetraffic amongst one or more physical or virtual server devices that hostcomputational instance 322. Load balancer 406A may simplify user accessby hiding the internal configuration of data center 400A, (e.g.,computational instance 322) from client devices. For instance, ifcomputational instance 322 includes multiple physical or virtualcomputing devices that share access to multiple databases, load balancer406A may distribute network traffic and processing tasks across thesecomputing devices and databases so that no one computing device ordatabase is significantly busier than the others. In some embodiments,computational instance 322 may include VPN gateway 402A, firewall 404A,and load balancer 406A.

Data center 400B may include its own versions of the components in datacenter 400A. Thus, VPN gateway 402B, firewall 404B, and load balancer406B may perform the same or similar operations as VPN gateway 402A,firewall 404A, and load balancer 406A, respectively. Further, by way ofreal-time or near-real-time database replication and/or otheroperations, computational instance 322 may exist simultaneously in datacenters 400A and 400B.

Data centers 400A and 400B as shown in FIG. 4 may facilitate redundancyand high availability. In the configuration of FIG. 4, data center 400Ais active and data center 400B is passive. Thus, data center 400A isserving all traffic to and from managed network 300, while the versionof computational instance 322 in data center 400B is being updated innear-real-time. Other configurations, such as one in which both datacenters are active, may be supported.

Should data center 400A fail in some fashion or otherwise becomeunavailable to users, data center 400B can take over as the active datacenter. For example, domain name system (DNS) servers that associate adomain name of computational instance 322 with one or more InternetProtocol (IP) addresses of data center 400A may re-associate the domainname with one or more IP addresses of data center 400B. After thisre-association completes (which may take less than one second or severalseconds), users may access computational instance 322 by way of datacenter 400B.

FIG. 4 also illustrates a possible configuration of managed network 300.As noted above, proxy servers 312 and user 414 may access computationalinstance 322 through firewall 310. Proxy servers 312 may also accessconfiguration items 410. In FIG. 4, configuration items 410 may refer toany or all of client devices 302, server devices 304, routers 306, andvirtual machines 308, any applications or services executing thereon, aswell as relationships between devices, applications, and services. Thus,the term “configuration items” may be shorthand for any physical orvirtual device, or any application or service remotely discoverable ormanaged by computational instance 322, or relationships betweendiscovered devices, applications, and services. Configuration items maybe represented in a configuration management database (CMDB) ofcomputational instance 322.

As noted above, VPN gateway 412 may provide a dedicated VPN to VPNgateway 402A. Such a VPN may be helpful when there is a significantamount of traffic between managed network 300 and computational instance322, or security policies otherwise suggest or require use of a VPNbetween these sites. In some embodiments, any device in managed network300 and/or computational instance 322 that directly communicates via theVPN is assigned a public IP address. Other devices in managed network300 and/or computational instance 322 may be assigned private IPaddresses (e.g., IP addresses selected from the 10.0.0.0-10.255.255.255or 192.168.0.0-192.168.255.255 ranges, represented in shorthand assubnets 10.0.0.0/8 and 192.168.0.0/16, respectively).

IV. Example Device, Application, and Service Discovery

In order for remote network management platform 320 to administer thedevices, applications, and services of managed network 300, remotenetwork management platform 320 may first determine what devices arepresent in managed network 300, the configurations and operationalstatuses of these devices, and the applications and services provided bythe devices, as well as the relationships between discovered devices,applications, and services. As noted above, each device, application,service, and relationship may be referred to as a configuration item.The process of defining configuration items within managed network 300is referred to as discovery, and may be facilitated at least in part byproxy servers 312.

For purposes of the embodiments herein, an “application” may refer toone or more processes, threads, programs, client modules, servermodules, or any other software that executes on a device or group ofdevices. A “service” may refer to a high-level capability provided bymultiple applications executing on one or more devices working inconjunction with one another. For example, a high-level web service mayinvolve multiple web application server threads executing on one deviceand accessing information from a database application that executes onanother device.

FIG. 5A provides a logical depiction of how configuration items can bediscovered, as well as how information related to discoveredconfiguration items can be stored. For sake of simplicity, remotenetwork management platform 320, public cloud networks 340, and Internet350 are not shown.

In FIG. 5A, CMDB 500 and task list 502 are stored within computationalinstance 322. Computational instance 322 may transmit discovery commandsto proxy servers 312. In response, proxy servers 312 may transmit probesto various devices, applications, and services in managed network 300.These devices, applications, and services may transmit responses toproxy servers 312, and proxy servers 312 may then provide informationregarding discovered configuration items to CMDB 500 for storagetherein. Configuration items stored in CMDB 500 represent theenvironment of managed network 300.

Task list 502 represents a list of activities that proxy servers 312 areto perform on behalf of computational instance 322. As discovery takesplace, task list 502 is populated. Proxy servers 312 repeatedly querytask list 502, obtain the next task therein, and perform this task untiltask list 502 is empty or another stopping condition has been reached.

To facilitate discovery, proxy servers 312 may be configured withinformation regarding one or more subnets in managed network 300 thatare reachable by way of proxy servers 312. For instance, proxy servers312 may be given the IP address range 192.168.0/24 as a subnet. Then,computational instance 322 may store this information in CMDB 500 andplace tasks in task list 502 for discovery of devices at each of theseaddresses.

FIG. 5A also depicts devices, applications, and services in managednetwork 300 as configuration items 504, 506, 508, 510, and 512. As notedabove, these configuration items represent a set of physical and/orvirtual devices (e.g., client devices, server devices, routers, orvirtual machines), applications executing thereon (e.g., web servers,email servers, databases, or storage arrays), relationshipstherebetween, as well as services that involve multiple individualconfiguration items.

Placing the tasks in task list 502 may trigger or otherwise cause proxyservers 312 to begin discovery. Alternatively or additionally, discoverymay be manually triggered or automatically triggered based on triggeringevents (e.g., discovery may automatically begin once per day at aparticular time).

In general, discovery may proceed in four logical phases: scanning,classification, identification, and exploration. Each phase of discoveryinvolves various types of probe messages being transmitted by proxyservers 312 to one or more devices in managed network 300. The responsesto these probes may be received and processed by proxy servers 312, andrepresentations thereof may be transmitted to CMDB 500. Thus, each phasecan result in more configuration items being discovered and stored inCMDB 500.

In the scanning phase, proxy servers 312 may probe each IP address inthe specified range of IP addresses for open Transmission ControlProtocol (TCP) and/or User Datagram Protocol (UDP) ports to determinethe general type of device. The presence of such open ports at an IPaddress may indicate that a particular application is operating on thedevice that is assigned the IP address, which in turn may identify theoperating system used by the device. For example, if TCP port 135 isopen, then the device is likely executing a WINDOWS® operating system.Similarly, if TCP port 22 is open, then the device is likely executing aUNIX® operating system, such as LINUX®. If UDP port 161 is open, thenthe device may be able to be further identified through the SimpleNetwork Management Protocol (SNMP). Other possibilities exist. Once thepresence of a device at a particular IP address and its open ports havebeen discovered, these configuration items are saved in CMDB 500.

In the classification phase, proxy servers 312 may further probe eachdiscovered device to determine the version of its operating system. Theprobes used for a particular device are based on information gatheredabout the devices during the scanning phase. For example, if a device isfound with TCP port 22 open, a set of UNIX®-specific probes may be used.Likewise, if a device is found with TCP port 135 open, a set ofWINDOWS®-specific probes may be used. For either case, an appropriateset of tasks may be placed in task list 502 for proxy servers 312 tocarry out. These tasks may result in proxy servers 312 logging on, orotherwise accessing information from the particular device. Forinstance, if TCP port 22 is open, proxy servers 312 may be instructed toinitiate a Secure Shell (SSH) connection to the particular device andobtain information about the operating system thereon from particularlocations in the file system. Based on this information, the operatingsystem may be determined. As an example, a UNIX® device with TCP port 22open may be classified as AIX®, HPUX, LINUX®, MACOS®, or SOLARIS®. Thisclassification information may be stored as one or more configurationitems in CMDB 500.

In the identification phase, proxy servers 312 may determine specificdetails about a classified device. The probes used during this phase maybe based on information gathered about the particular devices during theclassification phase. For example, if a device was classified as LINUX®,a set of LINUX®-specific probes may be used. Likewise, if a device wasclassified as WINDOWS® 2012, as a set of WINDOWS®-2012-specific probesmay be used. As was the case for the classification phase, anappropriate set of tasks may be placed in task list 502 for proxyservers 312 to carry out. These tasks may result in proxy servers 312reading information from the particular device, such as basicinput/output system (BIOS) information, serial numbers, networkinterface information, media access control address(es) assigned tothese network interface(s), IP address(es) used by the particular deviceand so on. This identification information may be stored as one or moreconfiguration items in CMDB 500.

In the exploration phase, proxy servers 312 may determine furtherdetails about the operational state of a classified device. The probesused during this phase may be based on information gathered about theparticular devices during the classification phase and/or theidentification phase. Again, an appropriate set of tasks may be placedin task list 502 for proxy servers 312 to carry out. These tasks mayresult in proxy servers 312 reading additional information from theparticular device, such as processor information, memory information,lists of running processes (applications), and so on. Once more, thediscovered information may be stored as one or more configuration itemsin CMDB 500.

Running discovery on a network device, such as a router, may utilizeSNMP. Instead of or in addition to determining a list of runningprocesses or other application-related information, discovery maydetermine additional subnets known to the router and the operationalstate of the router's network interfaces (e.g., active, inactive, queuelength, number of packets dropped, etc.). The IP addresses of theadditional subnets may be candidates for further discovery procedures.Thus, discovery may progress iteratively or recursively.

Once discovery completes, a snapshot representation of each discovereddevice, application, and service is available in CMDB 500. For example,after discovery, operating system version, hardware configuration, andnetwork configuration details for client devices, server devices, androuters in managed network 300, as well as applications executingthereon, may be stored. This collected information may be presented to auser in various ways to allow the user to view the hardware compositionand operational status of devices, as well as the characteristics ofservices that span multiple devices and applications.

Furthermore, CMDB 500 may include entries regarding dependencies andrelationships between configuration items. More specifically, anapplication that is executing on a particular server device, as well asthe services that rely on this application, may be represented as suchin CMDB 500. For example, suppose that a database application isexecuting on a server device, and that this database application is usedby a new employee onboarding service as well as a payroll service. Thus,if the server device is taken out of operation for maintenance, it isclear that the employee onboarding service and payroll service will beimpacted. Likewise, the dependencies and relationships betweenconfiguration items may be able to represent the services impacted whena particular router fails.

In general, dependencies and relationships between configuration itemsmay be displayed on a web-based interface and represented in ahierarchical fashion. Thus, adding, changing, or removing suchdependencies and relationships may be accomplished by way of thisinterface.

Furthermore, users from managed network 300 may develop workflows thatallow certain coordinated activities to take place across multiplediscovered devices. For instance, an IT workflow might allow the user tochange the common administrator password to all discovered LINUX®devices in a single operation.

In order for discovery to take place in the manner described above,proxy servers 312, CMDB 500, and/or one or more credential stores may beconfigured with credentials for one or more of the devices to bediscovered. Credentials may include any type of information needed inorder to access the devices. These may include userid/password pairs,certificates, and so on. In some embodiments, these credentials may bestored in encrypted fields of CMDB 500. Proxy servers 312 may containthe decryption key for the credentials so that proxy servers 312 can usethese credentials to log on to or otherwise access devices beingdiscovered.

The discovery process is depicted as a flow chart in FIG. 5B. At block520, the task list in the computational instance is populated, forinstance, with a range of IP addresses. At block 522, the scanning phasetakes place. Thus, the proxy servers probe the IP addresses for devicesusing these IP addresses, and attempt to determine the operating systemsthat are executing on these devices. At block 524, the classificationphase takes place. The proxy servers attempt to determine the operatingsystem version of the discovered devices. At block 526, theidentification phase takes place. The proxy servers attempt to determinethe hardware and/or software configuration of the discovered devices. Atblock 528, the exploration phase takes place. The proxy servers attemptto determine the operational state and applications executing on thediscovered devices. At block 530, further editing of the configurationitems representing the discovered devices and applications may takeplace. This editing may be automated and/or manual in nature.

The blocks represented in FIG. 5B are examples. Discovery may be ahighly configurable procedure that can have more or fewer phases, andthe operations of each phase may vary. In some cases, one or more phasesmay be customized, or may otherwise deviate from the exemplarydescriptions above.

In this manner, a remote network management platform may discover andinventory the hardware, software, and services deployed on and providedby the managed network. As noted above, this data may be stored in aCMDB of the associated computational instance as configuration items.For example, individual hardware components (e.g., computing devices,virtual servers, databases, routers, etc.) may be represented ashardware configuration items, while the applications installed and/orexecuting thereon may be represented as software configuration items.

The relationship between a software configuration item installed orexecuting on a hardware configuration item may take various forms, suchas “is hosted on”, “runs on”, or “depends on”. Thus, a databaseapplication installed on a server device may have the relationship “ishosted on” with the server device to indicate that the databaseapplication is hosted on the server device. In some embodiments, theserver device may have a reciprocal relationship of “used by” with thedatabase application to indicate that the server device is used by thedatabase application. These relationships may be automatically foundusing the discovery procedures described above, though it is possible tomanually set relationships as well.

The relationship between a service and one or more softwareconfiguration items may also take various forms. As an example, a webservice may include a web server software configuration item and adatabase application software configuration item, each installed ondifferent hardware configuration items. The web service may have a“depends on” relationship with both of these software configurationitems, while the software configuration items have a “used by”reciprocal relationship with the web service. Services might not be ableto be fully determined by discovery procedures, and instead may rely onservice mapping (e.g., probing configuration files and/or carrying outnetwork traffic analysis to determine service level relationshipsbetween configuration items) and possibly some extent of manualconfiguration.

Regardless of how relationship information is obtained, it can bevaluable for the operation of a managed network. Notably, IT personnelcan quickly determine where certain software applications are deployed,and what configuration items make up a service. This allows for rapidpinpointing of root causes of service outages or degradation. Forexample, if two different services are suffering from slow responsetimes, the CMDB can be queried (perhaps among other activities) todetermine that the root cause is a database application that is used byboth services having high processor utilization. Thus, IT personnel canaddress the database application rather than waste time considering thehealth and performance of other configuration items that make up theservices.

V. Automated Error Detection and Resolution

As used herein, the term “application” may refer to any form ofexecutable software, such as a program, process, thread, script, codemodule, or service.

As explained above, a remote network management platform may support thesimultaneous execution of numerous applications of varying types. Evenwith rigorous testing, these applications may exhibit errors, includingbut not limited to instability (e.g., crashes, freezes), incorrectoperation (e.g., providing wrong results), and/or undesirable behavior(e.g., excessive latency or resource utilization).

Detecting such errors can be difficult. Obvious errors, such as crashes,may be relatively straightforward to detect in some cases and oftenusers will complain when they occur. More subtle errors, on the otherhand, might be difficult to detect because users might ignore them ornot even realize that an error has occurred. Debugging such errors todetermine root cause can be much more complicated, as many applicationsrely on other applications, libraries, databases, remote servers, and soon. Thus, an error that presents itself in one application may have aroot cause in the design or implementation of another application.Further, once a root cause is identified, a resolution may not beapparent. In some cases, an application may need to be restarted. Inothers, parameters may be able to be changed to resolve the error.Moreover, some errors may only be experienced by certain users carryingout certain patterns of activities, and the application may otherwisebehave in the expected manner.

As a consequence, detection, root cause determination, and resolution oferrors can be an enormously complex process. Even resolving a singleerror in an application can take hours or days of effort, which subjectsusers to undesirable experiences or can leave the application in anunusable or unstable state. Clearly, the traditional methods cannotscale to today's large, multi-application platforms.

To address these and possibly other deficiencies, the embodiments hereininvolve automated error detection and resolution by way of a rule-basedframework. Advantageously, these embodiments can be adapted to detectand resolve a wide variety of errors, thus dramatically improvingplatform stability and performance.

FIG. 6 provides an example software architecture 600 for proactive errordetection and resolution. All of the functionality depicted inarchitecture 600 may be implemented on a single computational instance(e.g., computational instance 322) or possibly split across multiplecomputational instances. The main elements include proactive erroridentifier 602, error scenario mapper 604, scenarios 606A, 606B, 606C,and 606D, and fix scripts 608A, 608B, and 608C. In various embodiments,more or fewer of these elements may exist. For example, there may bemore or less than four scenarios and/or more or less than three fixscripts. In some implementations, proactive error identifier 602 anderror scenario mapper 604 may be separate applications. In others,proactive error identifier 602 error scenario mapper 604 may be parts ofthe same or a common application.

Proactive error identifier 602 is an application or set of applicationsconfigured to obtain information regarding errors experienced by otherapplications operating on computational instance 322. The categories ofthese errors may include explicit errors 602A (e.g., errors indicated,signaled or reported by an application), guided help triggers 602B(e.g., a series of questions presented to a user that identify the typeof error that a user might be experiencing with one or moreapplications), lifecycle events 602C (e.g., when new versions or patchesof an application become available), usage deviations from desiredpatterns 602D (e.g., when a user navigates through a series of web-basedresources in an unexpected order), and other channels 602E as well.Thus, various other error categories may be possible.

The operation of proactive error identifier 602 is illustrated in FIG.7. In arrangement 700, one or more applications 702 may use, access, orproduce information in various locations of a platform, such as logfiles 704, configuration files 706, messages 708, and/or databaseentries 710. The content at these locations (referred to as resources)may, in turn, be read or accessed by proactive error identifier 602 inorder to determine whether any errors related to applications 702 areidentified therein.

In some embodiments, applications 702 may represent more than justapplication-layer software. For sake of convenience, what is referred toas applications 702 may include kernel, device driver, back-end,mid-tier, middleware, library, server, or user-facing software, as justsome examples.

Log files 704 may be, for example, one or more system level log files,such as a syslog, event log, authentication log, kernel log, boot log,scheduled job (e.g., cron) log and so on. Alternatively or additionally,log files 704 may include application-level log files for mail services,web services, database services, and so on. These files may be stored inmain memory or written to persistent storage. Generally, each of logfiles 704 consists of a time-ordered series of entries (e.g., textstrings) written in accordance to a pre-established format. Theseentries may identify one or more of a timestamp, the source applicationof applications 702, a user of the source application, a severity, and amessage. Not all entries explicitly indicate errors, but some may (e.g.,when a source application is experiencing an error, it may write amessage indicating the error to a log file). Further, error conditionsmay be inferred from a series of entries (e.g., a series of repeated logentries from a source application may indicate that the sourceapplication is unable to operate in an expected or desirable manner).Advantageously, the pre-established format for log entries mayfacilitate pattern matching and parsing of these entries (e.g., by wayof regular expressions or finite state machines). Thus, proactive erroridentifier 602 may be able to programmatically determine errors from logfiles 704.

Configuration files 706 may be, for example, one or more filescontaining information used by an application of applications 702 tocontrol its initiation and/or operation. The application may read one ormore of configuration files 706 and apply the settings therein one ormore times over the course of execution. Some of applications 702 mayread from multiple configuration files. For instance, a web server mayhave a main configuration file as well as one or more secondaryconfiguration files for plugins or loadable modules. Not unlike logfiles, configuration files 706 may include textual content in apre-established format that is conducive to pattern matching and parsing(e.g., by way of regular expressions or finite state machines). In thismanner, proactive error identifier 602 may be able to programmaticallydetermine errors from configuration files 706. In some cases, proactiveerror identifier 602 may be able to identify possible errors inapplications 702 from improper or invalid data in configuration files706.

Messages 708 may be one or more sources of messages that may be providedby applications 702 or the underlying operating system of computationalinstance 322. These messages may be temporarily stored in message queuesor some other inter-application messaging system for example. Some ofthese messages may explicitly indicate or implicitly suggest certainerror conditions. In some cases, messages 708 may be sent tospecifically to proactive error identifier 602, and in other casesmessages 708 may be intended for another destination but ultimately readby proactive error identifier 602. Regardless, messages 708 may alsoconform to a pre-established format that facilitates pattern matchingand parsing (e.g., by way of regular expressions or finite statemachines). Accordingly, proactive error identifier 602 may be able toprogrammatically determine errors from messages 708.

Database entries 710 may include information written to rows of one ormore tables in a relational database or otherwise stored in anon-relational database, for example. Each row may include severaldistinct data elements (e.g., columns) of various types (e.g., textstring, numeric, referential). Given the strict formatting of eachdatabase entry, certain patterns of data within one entry or acrossmultiple entries may be indicative of an error. As with log files 704,database entries 710 may explicitly indicate errors or store a series ofentries from which error conditions may be inferred. In some cases,applications 702 may use such database tables for the purpose oflogging, and therefore the functionality and/or content of log files 704and database entries 710 may overlap to some extent.

Regardless of exact implementation, proactive error identifier 602 mayobtain information regarding the behavior of applications 702 from oneor more of these sources per application. In some embodiments, proactiveerror identifier 602 may do so on a regular basis (e.g., once everyminute, 5 minutes, 10 minutes as specified by a timer), based onpre-established triggers (e.g., signals from applications 702, log filemonitors, or database listeners), or on demand. From this data,proactive error identifier 602 may determine actual or likely errorevents and/or conditions.

Other sources not shown in FIG. 7 may be used as well. Thus, log files704, configuration files 706, messages 708, and database entries 710 arejust examples of sources.

Turning back to FIG. 6, proactive error identifier 602 may provideindications of errors that it has identified to error scenario mapper604. These indications may be in a raw form or in a preprocessed form.For example, proactive error identifier 602 may provide relevantportions of log files 704, configuration files 706, messages 708, and/ordatabase entries 710 indicative of errors to error scenario mapper 604.Alternatively, proactive error identifier 602 may process or summarizeidentified errors into a simplified form (e.g., a binary or textualvalue or set of values), and send this to error scenario mapper 604.

Error scenario mapper 604 may include a number of rules 604A thatassociate the indications of errors received from proactive erroridentifier to one or more of scenarios 606A, 606B, 606C, and 606D (whichmay also be referred to as “error scenarios”). Rules 604A may beabsolute, in the sense that they will result in at most one of scenarios606A, 606B, 606C, and 606D being associated with any particular error.Alternatively or additionally, rules 604A may be probabilistic in thatthey can associate more than one of scenarios 606A, 606B, 606C, and 606Dwith any particular error. In the latter case, error scenario mapper 604may associate a probability or confidence value with one or more ofscenarios 606A, 606B, 606C, and 606D. The higher this probability orconfidence value for a given scenario, the more likely that it is thecause of the particular error (at least, according to the determinationof error scenario mapper 604).

Rules 604A may take various forms, such as regular expressions, finitestate machines, SQL expressions, arithmetic or logical expressions,other types of pattern matchers, word or token frequency counts, sematicparsers, or any combination of these and/or other techniques. Rules 604Amay identify, for example, an error source (e.g., one or more files offiles 704, one or more files of configuration files 706, one or moremessages of messages 708, and/or one or more entries of database entries710), an expression or parser that can be used to specify a pattern inthe error indications from this error source (e.g., a regularexpression, finite state machines, SQL expression, arithmetic or logicalexpression, another type of pattern matcher, word or token frequencycount, and/or sematic parser), and then an indication of the scenario(s)of scenarios 606A, 606B, 606C, and 606D that is the suspected cause ofthe error condition.

In some embodiments, rules 604A may be in an ordered listing, and errorscenarios mapper 604 may apply each of rules 604A to the errorindications from proactive error identifier 602 in order until a matchis found. If no matches are found, then error scenario mapper 604 maydetermine that no actual errors have been found or that no actual errorscan be determined from the error indications.

Each of scenarios 606A, 606B, 606C, and 606D may be associated with oneor more of fix scripts 608A, 608B, and 608C. These fix scripts may beprograms that attempt to address the error conditions identified bytheir associated scenario(s). While referred to as “scripts” herein, fixscripts 608A, 608B, and 608C may each be one or more actual scripts,compiled programs, or other types of software code.

TABLE 1 Pattern Matcher/ Application Source Freq Parser Fix Script(s)mywebserver file://var/log/httpd-error.log  60 secs Look for “file notFile generator found” errors mywebserver file://var/log/httpd-access.log  5 secs Look for same user Page reloading same web refresher page 3 ormore times mywebserver file://etc/httpd/httpd.conf 3600 secs/ Check IPaddress Configuration on change binding file rewriter diskmonfile://var/log/syslog 1800 secs Look for reports of Garbage diskutilization over collector 90% myapp file://var/log/myapp-err.log  10secs Look for fatal errors App restarter myapp db://myapp-db/table1  60secs Look for invalid Database values integrity modifier

Fix scripts 608A, 608B, and 608C may carry out various operations, suchas terminating and restarting one or more applications (including butnot limited to an application that indicated an error), editing aconfiguration file, editing database entries, generating orre-generating application content or other data, and so on. Each ofscenarios 606A, 606B, 606C, and 606D may have a one-to-one associationwith fix scripts 608A, 608B, and 608C. However, in some cases, more thanone of scenarios 606A, 606B, 606C, and 606D may be associated with thesame fix script. In other cases, a single one of scenarios 606A, 606B,606C, and 606D may be associated with multiple fix scripts.

With regard to how rules 604A are specified, error scenario mapper 604may use or incorporate a mapping or table-like structure that listsapplications, sources of error detection for this application (e.g., inthe form of URLs), how frequently to check these sources (e.g., inseconds), a pattern matcher/parser to detect errors, and a reference toone or more fix scripts. An example of such a mapping is shown in Table1.

The frequencies in Table 1 are for purposes of the example and may vary.Further, the pattern matcher/parser of Table 1 includes any combinationof one or more regular expressions, finite state machines, SQLexpressions, arithmetic or logical expressions, word or token frequencycounts, sematic parsers, and/or other techniques.

The following subsections illustrate a number of error conditions thatcan be detected and possibly fixed by the system of architecture 600using the examples of Table 1. These examples, however, are far fromexhaustive and many others may exist.

A. Web Server “File Not Found” Errors

From time to time, certain links on a web site may not work as expected,in particular a web resource (e.g., web page) being sought by a usercannot be found by the web server. Such a resource may have beenaccidentally deleted or perhaps has not yet been generated from sourcedata. In either case, when a user seeks to load this resource by way ofa web browser, the web server will instead provide a “file not found”error, such as an HTTP 404 Not Found error. Receiving such error caninterrupt user workflow and cause frustration.

A rule for this scenario is shown in the first row of Table 1. Theapplication is identified as “mywebserver”, which may be the name of itsexecutable file. The source URL is “file://var/log/httpd-error.log”which identifies the file to which mywebserver logs errors. Thefrequency is once every 60 seconds. The pattern matcher/parser scansthis log file for “file not found” errors. The fix script is a filegenerator that generates the missing file, or at least a default filewith a helpful error message.

In other words, once every minute, the pattern matcher/parser is appliedto the httpd-error.log file. In some cases, the entire file isprocessed. In other cases, only new entries in the file that werecreated in the last 60 seconds (since the previous check of the file)are processed. If the pattern matcher/parser identifies one or morefiles that were not found, it provides the locations and names of thesefiles to the file generator fix script. Then, the file generator fixscript generates an appropriate file with the specified file name, andplaces it in the specified location. In this way, future requests forthe file will return a result.

B. Frequent Web Page Reloading

Occasionally a user may be waiting for a web page to refresh in order toobtain desired information therefrom. For instance, the refreshed webpage may contain the outcome of a task (e.g., test results for ane-learning module) or reflect the latest status of something in whichthe user is interested (e.g., that the state of an IT trouble ticket hasbeen modified). Web servers may refresh web pages based on triggers(e.g., changes in database entries related to the content to bedisplayed on the web page or reception of information to be displayed onthe web page). In some cases, web pages may dynamically generated fromdata in files and/or database tables. But, these generated web pagesmight be cached for some period of time (e.g., a few minutes). Thus, thecached web page might not reflect the latest changes to the files and/ordatabase tables. In such situations, a user expecting the web page todisplay these changes may manually refresh the web page some number oftimes in succession until the page is regenerated. This can lead to userconfusion and irritation.

A rule for this scenario is shown in the second row of Table 1. Theapplication is again “mywebserver”. The source URL is“file://var/log/httpd-access.log” which identifies the file to whichmywebserver logs the web pages requested by a user. These log entriesmay include a userid of an authenticated user, as well as a URL of therequested web page. The frequency is once every 5 seconds. The patternmatcher/parser scans this log file for the same user requesting the sameweb page at least 3 times within the 5-second period. The fix script isa page refresher that refreshes the requested page with the latestsource data.

Thus, once every 5 seconds, the pattern matcher/parser is applied to thehttpd-access.log file. In some cases, the entire file is processed. Inother cases, only new entries in the file that were created in the last5 seconds (since the previous check of the file) are processed. If thepattern matcher/parser identifies that the same user has requested acertain web page 3 or more times in the within the 5-second period, itprovides the path and name of the file to the page refresher fix script.Then, the page refresher fix script regenerates the web page from thelatest relevant information that is stored in main memory, the filesystem, and/or database entries. As a consequence, the user will be ableto obtain the sought after information (if it is available) in a muchquicker fashion—without having to wait for the cached page to time out.

C. Improper IP Address Binding

Server applications typically bind to TCP or UDP port numbers, as wellas IP addresses. In some configurations, servers may bind to a single IPaddress. However, on systems with multiple IP addresses, servers may beable to bind to some or all of these addresses. If a server isconfigured to bind to one or more specific IP addresses, an indicationof such may be stored in the server's configuration file. When thesystem changes IP addresses, the configuration file should be updatedaccordingly. However, this might not happen, resulting in the serverbeing unable to initiate or other errors.

A rule for this scenario is shown in the third row of Table 1. Theapplication is again “mywebserver”. The source URL is“file://etc/httpd/httpd.conf” which identifies the main configurationfile of mywebserver. This configuration file may be in the typical UNIX®form (e.g., with configurable settings appearing on one or more linesalong with their values). The frequency is once every 3600 seconds orwhen the configuration file changes. The latter functionality mayinvolve a watcher script that triggers whenever the configuration fileis edited or rewritten. The pattern matcher/parser scans theconfiguration file for the IP addresses to which mywebserver is to bind.The fix script is a configuration file rewriter that attempts to repairinvalid entries in the configuration file.

Therefore, once every 3600 seconds or upon detected change, the patternmatcher/parser is applied to the httpd.conf file. If the patternmatcher/parser detects that mywebserver is attempting to bind to one ormore invalid IP addresses, it implicitly or explicitly signals theconfiguration file rewriter fix script. Then, the configuration filerewriter fix script edits the configuration file so that myweb serverbinds only to valid IP addresses that are configured for use by thesystem. Thus, errors in the httpd.conf file can be detected andcorrected almost as quickly as they occur.

D. High Disk Utilization

A common cause of system failure is running out of useable disk space.For example, the amount of data stored by some applications (e.g., indatabases) or written to log files may grow to the point that there isno room left in the applicable disk partition. As a consequence, theseand other applications that rely on there being at least some amount ofdisk space may fail. In order to avoid these failures, disk utilizationgrowing beyond a threshold amount can be used as a trigger for cleaningup unneeded data stored on the disk.

A rule for this scenario is shown in the fourth row of Table 1. Theapplication is “diskmon”, which is assumed to be configured to checkdisk utilization periodically, and log readings of high diskutilization. The source URL is “file://var/log/syslog” which identifiesthe file to which these readings of high disk utilization are written.The frequency is once every 1800 seconds. The pattern matcher/parserscans the syslog file for messages indicating high disk utilization,over 90% for example. The fix script is a garbage collector thatattempts to reduce disk utilization. It may do this by deleting unneededtemporary files, deleting or compressing old log entries, defragmentingdatabases, and/or other activities.

Accordingly, once every 1800 seconds, the pattern matcher/parser isapplied to the syslog file. If the pattern matcher/parser detects thatdiskmon has logged messages indicating high disk utilization, executionof the garbage collector fix script is triggered. Then, the garbagecollector fix script attempts to reduce disk utilization. Thus, useabledisk space may be increased.

E. Fatal Application Errors

Not unlike web servers, other types of applications may also usededicated log files to record events such as errors. In some cases, anapplication that is experiencing a fatal error, from which it cannotrecover without being restarted, will indicate as such in a log file.These fatal errors could be crashes, faults, or other unexpectedoccurrences that render the application unusable for its intendedpurpose. Fatal errors may be clearly marked in the log file, for examplecontaining the text string “FATAL ERR”.

A rule for this scenario is shown in the fifth row of Table 1. Theapplication is “myapp”. The source URL is “file://var/log/myapp-err.log”which identifies the error log file of myapp. The frequency is onceevery 10 seconds. The pattern matcher/parser scans the myapp-err.logfile for log messages indicating a fatal error. The fix script is an apprestarter that attempts to re-execute, re-run, or otherwise reinitiatemyapp. That may include terminating some or all processes associatedwith myapp and restarting the application.

Therefore, once every 10 seconds, the pattern matcher/parser is appliedto the myapp-err.log file. If the pattern matcher/parser detects thatmyapp has logged one or more fatal error message since the last timethat myapp-err.log was checked, execution of the app restarter fixscript is triggered. Then, the app restarter fix script attempts torestart the application. In this manner, application failures arerapidly detected and corrected.

F. Invalid or Corrupted Database Content

Many modern applications rely to some extent on databases to storecontent, whether it is related to the configuration, input, or output ofthese applications. Therefore, it is critical that the information inthese databases is correct. Nonetheless, databases can be corrupted,thought application errors, manual editing by users, during an upgradeto a new schema, or from other causes. For example, in a relationaldatabase, values in a single row can be invalid in the sense that thereading application is not designed to process these values.Alternatively or additionally, certain values in multiple tables or rowsmay be expected to have a particular type of relationship that they donot. Common invalid values may include references to deleted columns orrows, as well as duplicated entries. When such corruption occurs, theapplications relying on the information may not be able to functionproperly.

A rule for this scenario is shown in the sixth row of Table 1. Theapplication is again “myapp”. The source URL is “db://myapp-db/table1”which identifies a tables within a myapp database. The frequency is onceevery 60 seconds. The pattern matcher/parser scans table1 for invalidvalues. The fix script is a database integrity modifier that attempts toeliminate these invalid values and/or replace them with valid values.For example, references to invalid rows or columns may be deleted orreplaced with references to valid rows or columns.

Thus, once every 60 seconds, the pattern matcher/parser is applied totable1. If the pattern matcher/parser detects that table1 containsinvalid values, execution of the database integrity modifier fix scriptis triggered. Then, the database integrity modifier fix script attemptsto clean the database in the fashion proscribed above or in other ways.Therefore, database integrity can be maintained.

G. Other Uses

The automated error detection and resolution techniques described hereincan be used for more than just the scenarios above. These techniques areflexible and can be adapted to many different types of situations whereapplication behavior on a remote network management platform is notoccurring in an expected fashion.

VI. Example Operations

FIG. 8 is a flow chart illustrating an example embodiment. The processillustrated by FIG. 8 may be carried out by a computing device, such ascomputing device 100, and/or a cluster of computing devices, such asserver cluster 200. However, the process can be carried out by othertypes of devices or device subsystems. For example, the process could becarried out by a computational instance of a remote network managementplatform or a portable computer, such as a laptop or a tablet device.

The embodiments of FIG. 8 may be simplified by the removal of any one ormore of the features shown therein. Further, these embodiments may becombined with features, aspects, and/or implementations of any of theprevious figures or otherwise described herein.

Block 800 may involve, possibly based on a pre-defined triggerassociated with a particular application, reading error data from aresource that is used by the particular application, wherein persistentstorage contains definitions of a plurality of error scenarios, aplurality of fix scripts, and associations between each of the pluralityof error scenarios and one or more of the plurality of fix scripts.These operations may be performed by an error identifier application.

Block 802 may involve applying one or more rules to the error data,wherein the rules involve pattern matching or parsing. These operationsmay be performed by an error scenario mapping application.

Block 804 may involve, possibly based on applying the one or more rules,determining a particular error scenario represented in the error data,wherein the particular error scenario is one of the plurality of errorscenarios. These operations may be performed by the error scenariomapping application.

Block 806 may involve determining, based on the associations, aparticular fix script associated with the particular error scenario,wherein the particular fix script is one of the plurality of fixscripts. These operations may be performed by the error scenario mappingapplication.

Block 808 may involve causing execution of the particular fix script.

In some embodiments, the error identifier application and the errorscenario mapping application are parts of a common application.

In some embodiments, determining the particular error scenariorepresented in the error data comprises determining a particular rule ofthe one or more rules through which the pattern matching or parsing ofthe error data indicates the particular error scenario.

In some embodiments, each particular rule of the one or more rulescontains a name of an application to which the particular rule applies,a location of the resource, a frequency at which the resource is to bechecked, a definition of a pattern matcher or parser to apply to data ofthe resource, and a specification of one or more of the plurality of fixscripts.

In some embodiments, the resource is an error log file, the particularerror scenario represented in the error data is that the particularapplication cannot find a file, and the particular fix script isconfigured to generate a version of the file.

In some embodiments, the resource is an access log file, the particularerror scenario represented in the error data is that the particularapplication is being requested to provide a file more than a thresholdnumber of times within a fixed period, and the particular fix script isconfigured to refresh the file from its source data.

In some embodiments, the resource is a configuration file, theparticular error scenario represented in the error data is that theconfiguration file contains invalid content, and the particular fixscript is configured to rewrite the configuration file with validcontent.

In some embodiments, the resource is a log file, the particular errorscenario represented in the error data is that storage utilization of astorage device within the system has exceeded a pre-defined threshold,and the particular fix script is configured to delete or compresscertain units of data on the storage device.

In some embodiments, the resource is a log file, the particular errorscenario represented in the error data is that the log file containsindications of fatal errors from the particular application, and theparticular fix script is configured to restart the particularapplication.

In some embodiments, the resource is a database table, the particularerror scenario represented in the error data is that the database tablecontains invalid values, and the particular fix script is configured torestore integrity of the database table.

In some embodiments, the pre-determined trigger is based on a timer ordetection of a modification to the resource.

VII. Closing

The present disclosure is not to be limited in terms of the particularembodiments described in this application, which are intended asillustrations of various aspects. Many modifications and variations canbe made without departing from its scope, as will be apparent to thoseskilled in the art. Functionally equivalent methods and apparatuseswithin the scope of the disclosure, in addition to those describedherein, will be apparent to those skilled in the art from the foregoingdescriptions. Such modifications and variations are intended to fallwithin the scope of the appended claims.

The above detailed description describes various features and operationsof the disclosed systems, devices, and methods with reference to theaccompanying figures. The example embodiments described herein and inthe figures are not meant to be limiting. Other embodiments can beutilized, and other changes can be made, without departing from thescope of the subject matter presented herein. It will be readilyunderstood that the aspects of the present disclosure, as generallydescribed herein, and illustrated in the figures, can be arranged,substituted, combined, separated, and designed in a wide variety ofdifferent configurations.

With respect to any or all of the message flow diagrams, scenarios, andflow charts in the figures and as discussed herein, each step, block,and/or communication can represent a processing of information and/or atransmission of information in accordance with example embodiments.Alternative embodiments are included within the scope of these exampleembodiments. In these alternative embodiments, for example, operationsdescribed as steps, blocks, transmissions, communications, requests,responses, and/or messages can be executed out of order from that shownor discussed, including substantially concurrently or in reverse order,depending on the functionality involved. Further, more or fewer blocksand/or operations can be used with any of the message flow diagrams,scenarios, and flow charts discussed herein, and these message flowdiagrams, scenarios, and flow charts can be combined with one another,in part or in whole.

A step or block that represents a processing of information cancorrespond to circuitry that can be configured to perform the specificlogical functions of a herein-described method or technique.Alternatively or additionally, a step or block that represents aprocessing of information can correspond to a module, a segment, or aportion of program code (including related data). The program code caninclude one or more instructions executable by a processor forimplementing specific logical operations or actions in the method ortechnique. The program code and/or related data can be stored on anytype of computer readable medium such as a storage device including RAM,a disk drive, a solid state drive, or another storage medium.

The computer readable medium can also include non-transitory computerreadable media such as computer readable media that store data for shortperiods of time like register memory and processor cache. The computerreadable media can further include non-transitory computer readablemedia that store program code and/or data for longer periods of time.Thus, the computer readable media may include secondary or persistentlong term storage, like ROM, optical or magnetic disks, solid statedrives, or compact-disc read only memory (CD-ROM), for example. Thecomputer readable media can also be any other volatile or non-volatilestorage systems. A computer readable medium can be considered a computerreadable storage medium, for example, or a tangible storage device.

Moreover, a step or block that represents one or more informationtransmissions can correspond to information transmissions betweensoftware and/or hardware modules in the same physical device. However,other information transmissions can be between software modules and/orhardware modules in different physical devices.

The particular arrangements shown in the figures should not be viewed aslimiting. It should be understood that other embodiments can includemore or less of each element shown in a given figure. Further, some ofthe illustrated elements can be combined or omitted. Yet further, anexample embodiment can include elements that are not illustrated in thefigures.

While various aspects and embodiments have been disclosed herein, otheraspects and embodiments will be apparent to those skilled in the art.The various aspects and embodiments disclosed herein are for purpose ofillustration and are not intended to be limiting, with the true scopebeing indicated by the following claims.

What is claimed is:
 1. A system comprising: persistent storagecontaining an error identifier application, an error scenario mappingapplication, definitions of a plurality of error scenarios, a pluralityof fix scripts, and associations between each of the plurality of errorscenarios and one or more of the plurality of fix scripts; and one ormore processors configured to: based on a pre-defined trigger associatedwith a particular application configured to execute on the system, read,by the error identifier application, error data from a resource that isstored on the system that is used by the particular application; apply,by the error scenario mapping application, one or more rules to theerror data, wherein the rules involve pattern matching or parsing; basedon applying the one or more rules, determine, by the error scenariomapping application, a particular error scenario represented in theerror data, wherein the particular error scenario is one of theplurality of error scenarios; determine, by the error scenario mappingapplication and based on the associations, a particular fix scriptassociated with the particular error scenario, wherein the particularfix script is one of the plurality of fix scripts; and cause executionof the particular fix script.
 2. The system of claim 1, wherein theerror identifier application and the error scenario mapping applicationare parts of a common application.
 3. The system of claim 1, whereindetermining the particular error scenario represented in the error datacomprises determining a particular rule of the one or more rules throughwhich the pattern matching or parsing of the error data indicates theparticular error scenario.
 4. The system of claim 1, wherein eachparticular rule of the one or more rules contains a name of anapplication to which the particular rule applies, a location of theresource, a frequency at which the resource is to be checked, adefinition of a pattern matcher or parser to apply to data of theresource, and a specification of one or more of the plurality of fixscripts.
 5. The system of claim 1, wherein the resource is an error logfile, wherein the particular error scenario represented in the errordata is that the particular application cannot find a file, and whereinthe particular fix script is configured to generate a version of thefile.
 6. The system of claim 1, wherein the resource is an access logfile, wherein the particular error scenario represented in the errordata is that the particular application is being requested to provide afile more than a threshold number of times within a fixed period, andwherein the particular fix script is configured to refresh the file fromits source data.
 7. The system of claim 1, wherein the resource is aconfiguration file, wherein the particular error scenario represented inthe error data is that the configuration file contains invalid content,and wherein the particular fix script is configured to rewrite theconfiguration file with valid content.
 8. The system of claim 1, whereinthe resource is a log file, wherein the particular error scenariorepresented in the error data is that storage utilization of a storagedevice within the system has exceeded a pre-defined threshold, andwherein the particular fix script is configured to delete or compresscertain units of data on the storage device.
 9. The system of claim 1,wherein the resource is a log file, wherein the particular errorscenario represented in the error data is that the log file containsindications of fatal errors from the particular application, and whereinthe particular fix script is configured to restart the particularapplication.
 10. The system of claim 1, wherein the resource is adatabase table, wherein the particular error scenario represented in theerror data is that the database table contains invalid values, andwherein the particular fix script is configured to restore integrity ofthe database table.
 11. The system of claim 1, wherein thepre-determined trigger is based on a timer or detection of amodification to the resource.
 12. A computer-implemented methodcomprising: based on a pre-defined trigger associated with a particularapplication, reading, by an error identifier application, error datafrom a resource that is used by the particular application, whereinpersistent storage contains definitions of a plurality of errorscenarios, a plurality of fix scripts, and associations between each ofthe plurality of error scenarios and one or more of the plurality of fixscripts; applying, by an error scenario mapping application, one or morerules to the error data, wherein the rules involve pattern matching orparsing; based on applying the one or more rules, determining, by theerror scenario mapping application, a particular error scenariorepresented in the error data, wherein the particular error scenario isone of the plurality of error scenarios; determining, by the errorscenario mapping application and based on the associations, a particularfix script associated with the particular error scenario, wherein theparticular fix script is one of the plurality of fix scripts; andcausing execution of the particular fix script.
 13. Thecomputer-implemented method of claim 12, wherein each particular rule ofthe one or more rules contains a name of an application to which theparticular rule applies, a location of the resource, a frequency atwhich the resource is to be checked, a definition of a pattern matcheror parser to apply to data of the resource, and a specification of oneor more of the plurality of fix scripts.
 14. The computer-implementedmethod of claim 12, wherein the resource is an error log file, whereinthe particular error scenario represented in the error data is that theparticular application cannot find a file, and wherein the particularfix script is configured to generate a version of the file.
 15. Thecomputer-implemented method of claim 12, wherein the resource is anaccess log file, wherein the particular error scenario represented inthe error data is that the particular application is being requested toprovide a file more than a threshold number of times within a fixedperiod, and wherein the particular fix script is configured to refreshthe file from its source data.
 16. The computer-implemented method ofclaim 12, wherein the resource is a configuration file, wherein theparticular error scenario represented in the error data is that theconfiguration file contains invalid content, and wherein the particularfix script is configured to rewrite the configuration file with validcontent.
 17. The computer-implemented method of claim 12, wherein theresource is a log file, wherein the particular error scenariorepresented in the error data is that storage utilization of a storagedevice has exceeded a pre-defined threshold, and wherein the particularfix script is configured to delete or compress certain units of data onthe storage device.
 18. The computer-implemented method of claim 12,wherein the resource is a log file, wherein the particular errorscenario represented in the error data is that the log file containsindications of fatal errors from the particular application, and whereinthe particular fix script is configured to restart the particularapplication.
 19. The computer-implemented method of claim 12, whereinthe resource is a database table, wherein the particular error scenariorepresented in the error data is that the database table containsinvalid values, and wherein the particular fix script is configured torestore integrity of the database table.
 20. An article of manufactureincluding a non-transitory computer-readable medium, having storedthereon program instructions that, upon execution by a computing system,cause the computing system to perform operations comprising: based on apre-defined trigger associated with a particular application, readingerror data from a resource that is used by the particular application,wherein persistent storage contains definitions of a plurality of errorscenarios, a plurality of fix scripts, and associations between each ofthe plurality of error scenarios and one or more of the plurality of fixscripts; applying one or more rules to the error data, wherein the rulesinvolve pattern matching or parsing; based on applying the one or morerules, determining a particular error scenario represented in the errordata, wherein the particular error scenario is one of the plurality oferror scenarios; determining, based on the associations, a particularfix script associated with the particular error scenario, wherein theparticular fix script is one of the plurality of fix scripts; andcausing execution of the particular fix script.